Fix bug resulting from changing v5's default solver #190
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
We removed the old solvers that were existing in parallel to the new ones in qutip v5. This broke a few tests.
qutip.Options
.qutip.Options
andqutip.SolverOptions
are equivalent and deprecated.mcsolve
can accept density matrix input, it usestate=
instead ofrho0=
.array(qobj)
should have been not working for a while now,full()
is the method preferred when converting to a numpy array.max_step
for one test... Unless there was a pulse thinner than the previous value and the solver happen to be lucky and find it previously, I don't understand why I had to reduce it that much. I hope that the idea in Keep the information of gate duration after the compilation #184, when implemented, will be able to bring some light on the issue.